System and method for displaying status of field devices

ABSTRACT

The invention is a system for monitoring the status of a field device having data including a data acquisition module, a first and a second diagnosis engine, and a client having a user input element for receiving user input status.

FIELD OF INVENTION

The invention relates to a system and method to display status of field devices.

BACKGROUND OF THE INVENTION

In prior art systems for monitoring field devices in a Plant, the statuses of the field devices are used to indicate the health of the devices and this is important for identifying the overall integrity of the Plant. The statuses of the devices are displayed in colours and values in various applications. These applications have different internal algorithms to calculate the status colour. Since different input data and algorithms are used for calculating the values of the status, the calculated values are of different types. Therefore, status values calculated from different applications are displayed separately. This is very inefficient and inconvenient for monitoring the overall Plant status generated from the different applications.

FIG. 1 is an example of a display according of the status calculated by one application. The display is an overall view of the field devices in a plant having a hierarchical relationship. The field devices and their status colour are displayed in an expandable parent folder. If there is more than one field device in a folder, the status colour having the most critical value is displayed for the folder.

There are cases where the calculated status colour is found to be incorrect after an operator has checked the field device physically. This is likely to be caused by an error in the algorithm or data retrieval.

Further, the status of the parent folder is not reflected accurately if the most critical value is from an unimportant field device.

Therefore, there is a need to enable a more accurate status display of the Plant.

SUMMARY OF THE INVENTION

The invention is a system for monitoring the status of field devices having data including a data acquisition module, a first and a second diagnosis engine, and a client having a user input element for receiving user input status.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example display in the prior art.

FIG. 2 is a preferred embodiment of the invention.

FIG. 3 is a process diagram of the invention.

FIGS. 4A and 4B are examples of a graphical user interface.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

FIG. 2 is an illustration of a preferred embodiment of the system 200 for monitoring the status of multiple field devices 202. A data acquisition module 204, referred to as Diagnosis Acquisition (DAQ) module, reads the actual status and data of the field devices 202. A first diagnosis engine 206, referred to as Basic Diagnosis Engine (BDE) interfaces with the DAQ module 204 to read the data from the field devices. The BDE 206 inputs the data from the field devices 202 into its repository of algorithms for calculating a first status of the field devices 202. The first calculated status is updated to a database 208, which is the Plant Resource Manager database (Resource Manager database).

A second diagnosis engine 210, an Advanced Diagnosis Server (ADS), interfaces with the DAQ 204 to read in the actual data from the field devices 202. The ADS 210 has the ability to execute applications, such as Plant Resource Manager Advance Diagnosis Application (PAA), containing complex algorithms, which have been specially designed to diagnose the status of a particular kind of device. Such applications are usually designed by the manufacturers of the field devices since they have full knowledge of the internal configuration of the field devices.

The applications apply the data from the field device to calculate a second status value which represents the status of the field device. Multiple applications for each field device can be run simultaneously to calculate the different kinds of status for each field device based on the device data retrieved from the DAQ 204. Examples of the device data include temperature and pressure. The second calculated statuses are written to the Resource Manager database 208.

The BDE 206 and the ADS 210 translate the calculated status to a predefined corresponding image for display on a graphical user interface. The value of the calculated status varies for different parameters and different field devices. It is more reader-friendly for the status to be represented by predefined images. For example, for colour images, “Red” is predefined for a value which is bad, “Green” for a good value and “Orange” for an intermediate value. Alternatively, the predefined images have different patterns.

A client 212, referred to as the Plant Resource Manager Client, interfaces with the Resource Manager database 208 for displaying the calculated first and the second statuses of the field devices on a graphical user interface. The client can also interface directly with the BDE 206 and the ADS 210 to obtain the calculated first and second statuses. In the client, there is a Diagnosis Window 214 for retrieving the relevant calculated status values for the field devices from the Resource Manager database 208 for display on a graphical user interface. The Diagnosis Window 214 can display a list of all the PAA modules which are assigned for a particular device. It is also able to display a list all the PAA modules assigned to all the field devices under a certain parent folder.

In the preferred embodiment, the client 212 has a user input element for receiving a user input status for each field device. The Diagnosis Window 214 is configurable to over-ride the calculated status of each field device with the user-input status. This allows an accurate representation of health of the field devices and hence the Plant.

The Resource Manager database 208 further includes an integration module 216 for integrating the calculated first and second statuses of the related field devices belonging to the same parent. The integration module 216 determines the most critical status value of the field devices belonging to the same parent or grandparent and displays the most critical status value with the name of the parent or grandparent.

Further, the client 212 has a graphical user interface element for a user to select the statuses of the field devices for display. Based on the selection, the Diagnosis Window 214 configures the graphical user interface to display the selected statuses and the corresponding images. The integration module 216 determines the most critical value for the parent or grandparent folder from the selected statuses. Thus, the status of the parent or grandparent folder is reflected without considering a non-selected status value, which is usually not critical or of no material relevance to the folder.

FIG. 3 shows one embodiment of the method in the invention.

In Step 301, the BDE 206 calculates the first status value for all the field devices 202 and translates the values to corresponding predefined images. The BDE 206 in Step 302 updates the Resource Manager database 208 with both the calculated values and the translated images.

In Step 303, the ADS 210 calculates the second status value for all the field devices 202 and translates the values to the corresponding predefined images. The ADS 210 in Step 304 updates the Resource Manager database 208 with both the calculated values and the translated images.

Steps 301, 302, 303 and 304 are performed periodically.

Step 305 displays on a graphical user interface in the Diagnosis Window 214, for all the field devices 202, the first and second statuses, the corresponding images, the user-input status and the checkboxes. Examples of the graphical user interface is shown in FIGS. 4A and 4B.

In FIG. 4A, the diagnostic items, for each respective type of status, are indicated in column 401. The name of the field device in column 402, the checkbox in column 403 and the corresponding image for the status in column 404. The checkboxes have mechanisms to include or exclude some or all diagnostic items for the field devices. If all the diagnostic items are excluded for a field device, the field device will not be included in the integration for the parent or grandparent folder.

In FIG. 4B, the graphical user interface further includes a list of all the field devices and their respective parent or grandparent folder. Reference numeral 411 shows a selected diagnostic item or diagnostic target, with marked checkbox. Reference numeral 412 shows the status for a device after integration. Reference numeral 413 shows the status for a folder after integration.

Referring back to FIG. 3, Step 306 allows a user to select the statuses of the field devices for display using a graphical user interface element. Preferably, the element is a checkbox.

Step 307 enables a user to save changes to the database after selecting the statuses of the field devices. Step 308 updates the images after the integration is completed. The updated images are displayed in Step 309. 

1. A system for monitoring the status of a field device having data including: a. a data acquisition module for reading the data of said field device; b. a first diagnosis engine interfacing with said data acquisition module and having a first repository of algorithms for calculating a first status of said field device; c. a second diagnosis engine interfacing with said data acquisition module and having a second repository of algorithms for calculating a second status of said field device; d. a client interfacing with said first diagnosis engine and said second diagnosis engine for displaying said calculated first status and said second status of said field device, and e. wherein said client further includes a user input element for receiving user input status.
 2. A system for monitoring the status of a plurality of field devices having data including: a. a data acquisition module for reading the status and data of said field devices; b. a first diagnosis engine interfacing with said data acquisition module and having a first repository of algorithms for calculating a first status of said field devices;. c. a second diagnosis engine interfacing with said data acquisition module and having a second repository of algorithms for calculating a second status of said field devices; d. a client interfacing with said first diagnosis engine and said second diagnosis engine for displaying said calculated first status and said second status of said field devices, and e. wherein said client further includes a user input element for receiving user input status.
 3. A system as claimed in claim 1 further including a database for said first and second diagnosis engines for storing the calculated first and second statuses, and said client interfacing with said database for: (i) displaying said calculated first status and said second status of said field device; and (ii) storing received user-input status.
 4. A system as claimed in claim 3 wherein said database further includes an integration module for integrating the calculated first and second status for related field devices.
 5. A system as claimed in claim 1 wherein said client further includes a graphical user interface element for a user to select statuses of field devices for display.
 6. A system as claimed in claim 5 wherein said graphical user interface element is a checkbox.
 7. A method of monitoring a field device having data information including the steps of: a. reading the data of said field device; b. calculating a first status of said field device from the read data with a first repository of algorithms and writing the first calculated status into said database; c. calculating a second status of said field device from the read data with a second repository of algorithms and writing the second calculated status into said database; and d. displaying said calculated first status and said second status of said field device on a user interface.
 8. A method of monitoring a plurality of field devices including the steps of: a. reading the data of said plurality of field devices; b. calculating first statuses of said plurality of field devices from the read data with a first repository of algorithms and writing the first calculated statuses into said database; c. calculating second statuses of said plurality of field devices from the read data with a second repository of algorithms and writing the second calculated statuses into said database; and d. displaying said calculated first statuses and said second statuses of said field devices on a graphical user interface.
 9. A method as claimed in claim 8, wherein said plurality of field devices are related, further including the step of integrating said calculated first and second statuses for said related field devices and displaying said integrated status.
 10. A method as claimed in claim 7, further including the steps of: providing a user input element on said user interface for a user to input status for each field device; receiving user-input status for each field device on said user interface; and updating the display status of each field device to the received status on said user interface.
 11. A method as claimed in claim 7 further including the steps of: translating said first and second calculated statuses into predefined corresponding first and second display images; and displaying said translated display image for said first and second calculated statuses.
 12. A method as claimed in claim 9 further including the steps of: providing a user input element on said user interface for user to input status for each field device; translating said received status into a predefined corresponding display image; and updating the display image of said field device to the corresponding display image for said received status.
 13. A method as claimed in claim 10 further including the steps of: translating said integrated status into the predefined corresponding display image for each field device; and updating the display image of each field device to the corresponding image for said integrated status.
 14. A method as claimed in claim 7 further including the step of providing a graphical user interface element for a user to select a preferred status for display, from said calculated first status, said second status or said user-input status.
 15. A method as claimed in claim 14 further including the step of updating the selection to said database.
 16. A method as claimed in claim 7 wherein said user input element is a checkbox.
 17. A method as claimed in claim 7 wherein said predefined display images are represented by different colors.
 18. A method as claimed in claim 7 wherein said predefined display images are represented by different patterns.
 19. A method as claimed in claim 8, further including the steps of: providing a user input element on said user interface for a user to input status for each field device; receiving user-input status for each field device on said user interface; and updating the display status of each field device to the received status on said user interface.
 20. A method as claimed in claim 8 further including the steps of: translating said first and second calculated statuses into predefined corresponding first and second display images; and displaying said translated display image for said first and second calculated statuses. 